Where _n_a_m_e is a string or an identifier (following the standard C
conventions) and _h_e_l_p_t_e_x_t is a string containing a description of what
the rules described by this set of templates are designed to do. This
will appear at the top of the help text in the Edit Global Parameters
dialog box in ppppmmmmrrrruuuulllleeeessss so it should be something that the user editing the
templates will understand. ppppmmmmrrrruuuulllleeeessss does not do line breaking, so
sensible use of newlines within the _h_e_l_p_t_e_x_t is encouraged.
PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss
Parameter definitions (both global and local) have the following form:
_n_a_m_e _v_a_l_u_e _a_t_t_r_l_i_s_t;;;;
Where an _n_a_m_e is an identifier (following the standard C conventions),
and _a_t_t_r_l_i_s_t consists of a list of whitespace separated _a_t_t_r_i_b_u_t_e====_v_a_l_u_e
pairs.
The following _a_t_t_r_i_b_u_t_es are defined for parameters:
ttttyyyyppppeeee Defines a type for the parameter. ppppmmmmrrrruuuulllleeeessss may be able to validate
user input for simple types such as integers. For more complex
types such as metric instance lists, checking may not be possible
(e.g. if a host is down the set of valid instances is unknown).
Valid values for ttttyyyyppppeeee are: ssssttttrrrriiiinnnngggg, ssssttttrrrroooonnnngggg (a non-null string),
ddddoooouuuubbbblllleeee, iiiinnnntttt, uuuunnnnssssiiiiggggnnnneeeedddd, %%%% (a percentage), hhhhoooosssstttt, hhhhoooossssttttlllliiiisssstttt, iiiinnnnsssstttt (a
single valid instance of a performance metric), iiiinnnnssssttttlllliiiisssstttt (a list of